Fix vulnerable System.Security.Cryptography.Xml via updating Microsoft.Extensions to 10.0.7 - #1260

Due to reports of incompatibilities with ASP.NET Core Data Protection (see dotnet/aspnetcore#66335), converting this to draft until it's confirmed stable (sounds like that will be in 10.0.7).

Note that any users affected can still override the installed version of this package manually to address the vulnerability concern, particularly if they are not using ASP.NET Core Data Protection. This is not a vulnerability in our library.

Edit: We are currently using 8.0.3 in this PR, not 10.0.6, but out of caution I'm still going to hold off a few days just in case there are users regularly running off latest master. I am unsure if the effect is the same for ASP.NET Core Data Protection 8.x. Also, separately I will look into upgrading our packages from 8.x to 10.x after this is merged.

10.0.7 was released with the regression fix, and it pulls in the vulnerability-fixed version of System.Security.Cryptography.Xml transitively, so I went ahead and upgraded all of our Microsoft.Extensions libraries to be on the same 10.0.7 version. That let me remove the manual installation of this package from the prior commit.

Note that just like the 8.x versions of the Microsoft.Extensions packages, the 10.x versions support netstandard2.0 and net462 just like our baseline targets.